W-21449660 new feature to manage dynamic client registration#453
W-21449660 new feature to manage dynamic client registration#453valkyrie69 wants to merge 11 commits intolatestfrom
Conversation
Co-authored-by: Isaac Eldridge <isaaceldridge@gmail.com>
| . Click *Save*. | ||
|
|
||
| [IMPORTANT] | ||
| Client management only applies to clients created after you enable this feature. Clients created before enabling this setting don't have the required registration data and can't be updated or deleted through Anypoint Platform. |
There was a problem hiding this comment.
I think we can re-word it to give more details:
It is recommended that you create a new client provider if you want to use Use registration credentials for client management for consistency.
Before we this feature is available, we don't save registration_access_token and registration_client_uri. After this feature is available, we save the info. If you don't enable "Use registration credentials", we use the existing mechanism. If you enable it, we start using registration_access_token and registration_client_uri that may cause a change in behavior.
| === How Client Management Works | ||
|
|
||
| These examples show PUT and DELETE requests that Anypoint Platform makes. | ||
| When you enable client management, Anypoint Platform handles update and delete operations based on what your IdP provides during client registration. |
There was a problem hiding this comment.
User enable client management in IDP using the option below
"Enable client deletion and updates in IdP"
If the user also select "Use registration credentials", we use registration_access_token and registration_client_uri if IDP return them. If IDP don't return them, we use existing mechanism
Writer's Quality Checklist
Before merging your PR, did you: